Skip to content

Conversation

@p3ck
Copy link

@p3ck p3ck commented Jul 29, 2025

azure_service_bus plugin has been moved to
azure.azcollection.azure_service_bus and will be removed in a future release.

This is my first time deprecating a module that has moved so I may have missed something. Thank you

azure_service_bus plugin has been moved to
azure.azcollection.azure_service_bus and will be removed in a future
release.
@github-actions
Copy link

Label error. Requires exactly 1 of: bug, chore, enhancement, major, minor, patch, skip-changelog. Found:

Copy link
Contributor

@Alex-Izquierdo Alex-Izquierdo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need to discuss and analyze this change and the desired behavior, ansible-rulebook, unlike ansible-core, does not support right now the deprecation capabilities that this PR assumes

cc @ptoscano

Copy link
Contributor

@ptoscano ptoscano left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @p3ck,

thanks for approaching us about the Azure EDA event source.

I noted inline why the current PR cannot work: as also @Alex-Izquierdo wrote, there is no support in ansible-rulebook/eda-server for any of the module lifecycle feature that ansible-playbook supports. I think what only works is marking the EDA module as deprecated in its DOCUMENTATION block.

Comment on lines +46 to +47
dependencies:
azure.azcollection: ">=3.7.0"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think this collection should start to pull other collections. Deprecating means that users should switch away from "something", while that "something" still works as-is until its removal.

hosts: all
sources:
- ansible.eda.azure_service_bus:
- azure.azcollection.azure_service_bus:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think this is correct: this example correctly refers to the module shipped in this collection, so it is valid until the module is shipped in the collection.

Most likely this rulebook ought to be copied together with the non-deprecated version of azure_service_bus, and the rulebook in that location ought to refer to the new location of the EDA source.

Comment on lines +41 to +47
azure_service_bus:
redirect: azure.azcollection.azure_service_bus
deprecation:
removal_version: 3.0.0
warning_text: >-
azure_service_bus has been moved to azure.azcollection.azure_service_bus.
Please update your tasks.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This does not work: there is no support in ansible-rulebook for deprecating/renaming/removing content as documented here:
https://docs.ansible.com/ansible/latest/dev_guide/module_lifecycle.html

@p3ck
Copy link
Author

p3ck commented Aug 26, 2025

Hello,

I was on PTO for the last few weeks so just getting back to this now. It doesn't seem like any of my changes to deprecate the module from here will work. Do you have any suggestion on how to proceed?

Thanks,
Bill

@Alex-Izquierdo
Copy link
Contributor

Hello,

I was on PTO for the last few weeks so just getting back to this now. It doesn't seem like any of my changes to deprecate the module from here will work. Do you have any suggestion on how to proceed?

Thanks, Bill

@p3ck I think that, as a short-term solution, we are going to deprecate it through documentation only. Enabling such deprecation behavior in ansible-rulebook would require a bigger effort, and I believe it’s not part of our short-term plans.

What we can also do is print a deprecation warning message at the start of the module.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants